Dynamic user interface control system

ABSTRACT

Methods and systems for providing a graphical user interface to a computing device are described. In one aspect, a method includes: providing a first portion of the graphical user interface to the computing device, the first portion of the graphical user interface including an interface element for receiving input through an input interface associated with the computing device; receiving input received at the interface element; determining an eligibility metric based on the input; comparing the eligibility metric to eligibility criteria; and when the eligibility metric does not satisfy the eligibility criteria, providing, to the computing device, a second portion of the graphical user interface, the second portion of the graphical user interface having a greater completion complexity than a third portion of the graphical user interface, the third portion of the graphical user interface being provided when the eligibility metric satisfies the eligibility criteria.

FIELD

The present application generally relates to dynamic control of a userinterface associated with a computing device and, more particularly, tocontrolling user interfaces to selectively increase or decrease acompletion complexity associated with such user interfaces to indirectlycontrol the use of computing resources.

BACKGROUND

Internet servers sometimes allow for the receipt of documents from anumber of different users. Some such systems may have little or nocontrol over the timing at which documents may be submitted. Forexample, there may be periods during which no documents are received andthere may be other periods when a large volume of documents arereceived. Often, system infrastructure is designed to accommodatedocument submission spikes. Designing systems capable of accommodatingsuch spikes, however, requires systems that have relatively highbandwidth, processing power, memory, etc., and such systems can becostly and may use a great deal of energy to operate. Furthermore, evenwhen systems are designed to accommodate document submission spikes, anatypical spike may occur that exceeds capacity.

For example, document submission spikes may occur in a system that isconfigured to process insurance documents, such as insuranceapplications, received from remote computing devices. The time of daymay affect the number of documents that are submitted or a notablecurrent event, such as a celebrity death, may result in a rapid rise inthe number of insurance documents being submitted to an insuranceprocessing system.

Insurance processing systems also suffer from other computing resourceproblems apart from those caused by submission spikes. For example, eachelectronic document that is received consumes computing resources sinceeach document occupies computer memory to store information associatedwith such documents. A significant volume of applications received overa lengthy period of time may occupy a significant amount of memory. Forexample, electronic insurance applications may be continually stored inmemory while insurance is in force since inaccuracies on the insuranceapplication may affect future claims. Given the importance of suchdocuments, storage may be redundant, meaning that each application maybe stored multiple times and each application may, therefore, consumecomputing memory resources that may be many multiples of the size of theelectronic application.

Over time the storage burden may become increasingly onerous and, astime elapses it may become increasingly difficult to identify items thatmay be purged from memory.

There is a need for improving the use of computing resources forelectronic document processing systems.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made, by way of example, to the accompanyingdrawings which show example embodiments of the present application, andin which:

FIG. 1 diagrammatically shows an example system;

FIG. 2 is a block diagram illustrating components of an examplecomputing device;

FIG. 3 shows, in flowchart form, a method for providing a graphical userinterface; and

FIG. 4 shows an example signal diagram for communications between aserver and a remote computing device to provide a graphical userinterface.

Similar reference numerals may have been used in different figures todenote similar components.

DESCRIPTION OF EXAMPLE EMBODIMENTS

In a first aspect, the present application may describe a server toprovide a graphical user interface to a computing device. The serverincludes a processor and a communication system coupled to the processorfor communicating over a network with the computing device. The serverfurther includes memory coupled to the processor. The memory storesprocessor-readable instructions that, when executed, cause the processorto: provide, via the communication system and to the computing device, afirst portion of the graphical user interface, the first portion of thegraphical user interface including an interface element for receivinginput through an input interface associated with the computing device;receive, via the communication system, input received at the interfaceelement; determine an eligibility metric based on the input; compare theeligibility metric to eligibility criteria; and when the eligibilitymetric does not satisfy the eligibility criteria, provide, to thecomputing device via the communication system, a second portion of thegraphical user interface, the second portion of the graphical userinterface having a greater completion complexity than a third portion ofthe graphical user interface, the third portion of the graphical userinterface being provided when the eligibility metric satisfies theeligibility criteria.

In another aspect, the present application may describe s method ofproviding a graphical user interface to a computing device. The methodmay include: providing a first portion of the graphical user interfaceto the computing device, the first portion of the graphical userinterface including an interface element for receiving input through aninput interface associated with the computing device; receiving inputreceived at the interface element; determining an eligibility metricbased on the input; comparing the eligibility metric to eligibilitycriteria; and when the eligibility metric does not satisfy theeligibility criteria, providing, to the computing device, a secondportion of the graphical user interface, the second portion of thegraphical user interface having a greater completion complexity than athird portion of the graphical user interface, the third portion of thegraphical user interface being provided when the eligibility metricsatisfies the eligibility criteria.

In yet a further aspect, the present application may describenon-transitory computer-readable media storing computer-executableprogram instructions which, when executed, configure a processor toperform one or more of the described methods. In this respect, the termprocessor is intended to include all types of processing circuits orchips capable of executing program instructions.

Other aspects and features of the present application will be understoodby those of ordinary skill in the art from a review of the followingdescription of examples in conjunction with the accompanying figures.

In the present application, the term “and/or” is intended to cover allpossible combinations and sub-combinations of the listed elements,including any one of the listed elements alone, any sub-combination, orall of the elements, and without necessarily excluding additionalelements.

In the present application, the phrase “at least one of . . . or . . . ”is intended to cover any one or more of the listed elements, includingany one of the listed elements alone, any sub-combination, or all of theelements, without necessarily excluding any additional elements, andwithout necessarily requiring all of the elements.

In at least some aspects, the present disclosure describes techniquesfor indirectly controlling the use of system resources associated with aback-end computing system, such as a server, by varying a graphical userinterface (GUI) that is configured to interact with the back-endcomputing system. More specifically, a graphical user interface that isused to submit data to a server may be selectively modified to makesubmission easier or more difficult. For example, as data that wasreceived as input at a remote computing device is being submitted to theserver, the server may evaluate the data to determine an eligibilitymetric. The eligibility metric may be a measure of the likelihood of auser being eligible for a service, such as insurance. The eligibilitymetric may, for example, be a score.

The server may compare the eligibility metric to predefined eligibilitycriteria and may modify the graphical user interface to make submissionmore complex based on the comparison. For example, when the eligibilitymetric suggests a likelihood of ineligibility, the server mayautomatically provide a relatively complex version of the graphical userinterface. The relatively complex version of the graphical userinterface is a version of the graphical user interface that is morecomplex than a version of the graphical user interface that is providedwhen the eligibility metric does not suggest ineligibility. The complexversion of the GUI is an artificially complex version of the graphicaluser interface that is used to either slow down submission or toincrease the abandonment rate of submissions to reduce the use ofcomputing resources.

The complex version of the GUI may be used, for example, to managebandwidth and other computing resources when there is a spike (e.g., arapid increase) in application submission. Some users may be providedwith the non-complex version of the GUI and others may be provided withthe complex version of the GUI. The complex version of the GUI may takelonger to complete than the non-complex version of the GUI and may havea higher drop-off rate. The complex version of the GUI may be used toeffectively manage the time at which submissions through the GUI areexpected to be received or to manage the number of submissions throughthe GUI that are expected to be received. For example, the complexversion of the GUI may allow at least some of the submissions to bereceived after the spike in application volume has ended.

The complex version of the GUI may use various techniques that make itmore complex than the less complex version of the GUI. For example, thecomplex version of the GUI may include a false interface element whereasthe less complex version of the GUI may not include the false interfaceelement. This false interface element may also be referred to as a dummyinterface element and may be an interface element that prompts for inputwhich, once received, is not used. For example, the input may not besent to the server or may not be used by the server and may, instead, bedisposed of.

The complex version of the GUI may increase complexity by disabling anauto-completion feature which is enabled on the less complex version ofthe GUI. The auto-completion feature may allow certain fields to beautomatically populated with input. For example, the auto-completionfeature may allow fields that receive identification information (e.g.,a name, address, date of birth, gender, email address, telephone number,etc.) to be automatically populated with previously storedidentification information. The previously stored identificationinformation is information that was previously input by a past user of acomputing device that is displaying the GUI. By disabling theauto-completion feature, the user is required to manually input moreinformation than if the auto-completion feature were enabled, makinginput more complex and slowing down entry.

The complex version of the GUI may, in at least some embodiments,increase complexity by enforcing a formatting restriction that is notenforced on the less complex version of the GUI. The formattingrestriction may, for example, be a date formatting restriction, anumerical formatting restriction, a name formatting restriction, acurrency formatting restriction, or a formatting restriction of anothertype. By way of example, the GUI may include a “date of birth” field, ora field which requests a date of another type and the complex version ofthe GUI may require the date to be input in a single format (e.g.,MM-DD-YYYY) whereas the less-complex version may allow for input with agreater number of formats.

By way of further example, the formatting restriction may be a nameformatting restriction which requires an inputted name to accord to apredetermined format. For example, the complex version of the GUI mayrequire a first name to be input prior to a last name and may generatean error when a last name is input first, whereas the less-complexversion of the GUI may allow for input of last name first and mayrecognize last name first formatting when a comma is used in a namefield.

The complex version of the GUI may, in at least some embodiments,increase complexity through the use of font size. For example, bothversions of the GUI may include some common text and the font size of atleast a portion of the common text may be different on the complexversion of the GUI than on the non-complex version of the GUI. Forexample, the font for such text on the complex version may be one thatis relatively more difficult to read than the font on the non-complexversion. For example, the font on the complex version may be a higherfont size; for example, a font that does not fit well on the page. Byway of further example, the font on the complex version may be a smallerfont size; for example, one that is difficult to read.

The complex version of the GUI may, in at least some embodiments,override a preference, such as a browser preference, that is notoverridden by the non-complex version of the GUI. For example, thenon-complex version of the GUI may use a default font size for thebrowser, whereas the complex version may override the default font size(e.g., by specifying an absolute size or by specifying a relative fontsize that is greater than or less than the default font size).

The non-complex version of the GUI may, in at least some embodiments,include completion instructions that are not immediately provided on thecomplex version of the GUI. The completion instructions may, forexample, specify a formatting restriction. For example, the GUI mayinclude a field that requires data to be input in a particular formatand the non-complex version may display the formatting restriction tothe user when the field is displayed. The complex version may includethe same field and may enforce the same formatting restriction for thatfield but may not display the formatting restriction to the user whenthe field is displayed. Instead, the complex version may generate anerror when a user attempts to submit a completed form. The error maydisplay the formatting restriction to the user.

The complex version of the GUI may, in at least some embodiments,include content that is unnecessarily verbose. For example, the complexversion may include text that is similar in content to text included inthe non-complex version but which has a higher word count than the textincluded in the non-complex version.

Conveniently, in obtaining an eligibility metric based on apartially-submitted electronic application and using the eligibilitymetric to selectively provide a complex or non-complex version of agraphical user interface, a server is provided with some control overthe use of computing resources. Further, since the eligibility metric isevaluated against eligibility criteria, computing resources may bedynamically managed by adjusting the eligibility criteria in response tochanges in network conditions. For example, during periods of peakusage, the eligibility criteria may be automatically adjusted by theserver to increase the number of computing devices that will receive thecomplex version of the GUI thereby delaying at least some submissions ordecreasing a submission rate. Later, when network conditions return tonormal, the eligibility criteria may be re-adjusted.

Reference is now made to FIG. 1, which shows an example system 10. Thesystem 10 includes a remote computing device 20 and a server 30. Theserver is configured to provide a graphical user interface to the remotecomputing device and the server may be a web server.

The server 30 and remote computing device 20 are configured tocommunicate digitally over one or more networks 40, which may includepublic networks (e.g. the Internet), private networks, VPNs, wirednetworks, wireless networks, and combinations thereof. The server 30 maybe implemented using one or more computing devices having processingresources and memory resources, being configured to receive and respondto requests from computing devices.

The remote computing device 20 may, in some embodiments, be a personalcomputer such as a laptop or desktop computer. In some embodiments, itis a mobile device, such as a smartphone, tablet, phablet, smartwatch,or combination thereof.

The server 30 and remote computing device 20 are both computing devicesand an example computing device 21 will now be described with referenceto FIG. 2.

The computing device 21 includes at least one processor 22, memory 24and a communication system 26. The communication system 26 may includesubsystems for wired or wireless data communication and wired orwireless voice communication. In some examples of the computing device21 which may be used, for example, with the remote computing device 20of FIG. 1, the communication system 26 includes a subsystem for cellulardata and voice connectivity via a cellular system 12. The cellularsystem 12 may include a system operating in accordance with one or moreof a variety of cellular voice and data protocols for connectivity andcommunication, including 5G, 4G and 3G systems. The communication system26 may further include a subsystem for wireless local area network(WLAN) connectivity with an access point, which may operating inaccordance with the IEEE 802.11 protocol, for example. The communicationsystem 26 may provide the computing device 21 with other wired orwireless connections for accessing the networks 40.

The computing device 21 may include a display 28 and/or one or moreinput interfaces associated with one or more input devices 36. The inputdevices 36 may include a touch sensitive overlay on the display 28 fordetecting touch-based input, for example. Other examples of the inputdevice 36 may include a keyboard, keypad, touchpad, motion sensor suchas a gyroscope or accelerometer, mouse, microphone, keyboard withtouch-sensitive surface, or various buttons. In some cases, the inputdevice 36 includes a port or other communication path for receivinginput via an external peripheral device, such as a mouse, keyboard,wand, pen, smartphone, smartwatch, etc.

The memory 24 may include volatile and non-volatile memory. At least apart of the memory 24 may store processor-readable instructions that,when executed by the processor, cause the processor to carry out some ofthe operations described herein. The processor-readable instructionsstored in memory 24 may include an operating system 44 that implementsbasic device functions and creates a run-time environment within whichother software is executed. The memory 24 may also store a plurality ofapplications 42, where the term “application” refers to a set ofprogram-executable instructions that configure or adapt the processor 22to carry out a particular algorithm or set of steps or operations.Example applications 42 may include a messaging application, a wordprocessing application, a calculator, a calendar, a music library, asocial media application, or other such applications. The nature of theapplications 42 will depend on whether the computing device 21 is theserver 30 or the remote computing device 20. For example, the remotecomputing device 20 may include an application 42, such as a browser,that is configured to enable functions of methods described herein asbeing performed by the remote computing device 20. Such functions mayinclude the capability to render a GUI on the display 28 based on datareceived from the server 30 and the ability to receive input to allow auser to interact with the GUI, the ability to provide auto-completionfunctions for populating one or more fields of a form based on storeddata and other functions such as those generally described herein.

A computing device 21 that is the server 30 may include an application42, which may be referred to as a GUI manager, which may enable theserver 30 to perform server functions as generally described herein. Forexample, such functions may include the ability to cause the GUI to berendered on a display 28 of the remote computing device 21 (e.g., byserving the GUI to the remote computing device 21), the ability todynamically modify the GUI to manage computing resources, and otherfunctions such as those generally described herein.

Reference is now made to FIG. 3, which shows, in flowchart form, anexample method 300 of providing a graphical user interface to acomputing device. In this example method 300, the described operationsare carried out by the server 30 (FIG. 1) and involve interactions withthe remote computing device 20. The method 300 may be implemented, atleast in part, through processor-executable instructions in anapplication 42, such as the GUI manager, although in some otherembodiments one or more of the operations is implemented viaprocessor-executable instructions in another application 42 or in theoperating system 44.

At operation 302, the server 30 provides a first portion of thegraphical user interface to the remote computing device 20. The firstportion of the graphical user interface may be provided as a web page.For example, the remote computing device 20 may request the web page(e.g., using an HTTP GET) and the server 30 may then provide the webpage through a communication system of the server. The web page includesinterface elements for receiving input through an input interfaceassociated with the remote computing device 20. The interface elementsmay be a displayed interactive feature that allows for receipt of inputthrough a suitable input device, such as a keyboard, touchscreen,microphone, etc.

By way of example, the first portion of the GUI may include a form. Theform may include one or more fields through which input may be received.By way of example, the fields may prompt a user for input of informationof a certain type. For example, the form may prompt the user for inputof a claims history, identification information such as a name, address,date of birth, contact information, medical history, etc.

A user of the remote computing device 20 may populate an interfaceelement, such as a field by interacting with the input device associatedwith the remote computing device. For example, in at least someembodiments, a user may interact with a keyboard to input a text-basedinput into a field. By way of further example, in some embodiments, auser may use an auto-completion feature. The auto-completion feature mayallow one or more interface elements (e.g., fields) to be automaticallypopulated based on input provided in similar interface elements in aprior session. For example, a name field may be automatically populatedwith a name that was entered into a form previously on the remotecomputing device 20.

Input may be received at the interface element and may be sent to theserver 30 from the remote computing device 20. For example, the remotecomputing device 20 may send the input using an HTTP POST upon receiptof suitable input, such as activation of a “save”, “send” or “submit”interface element.

At operation 303, the server 30 receives the input that was received atthe remote computing device 20 through the interface element. The server30 may receive the input through the communication system.

In response to receiving the input, the server 30 may determine aneligibility metric based on the input. The eligibility metric isdetermined based on one or more predefined rules or scores, which may bestored in memory associated with the server 30. For example, theeligibility metric may be determined as a score that is based on aplurality of inputs received from through the GUI. For example, certainresponses may have certain numerical values associated therewith and ahigher (or lower as the case may be) value may indicate a preferredresponse. For example, a user with no claims history may receive a scoreof 10 for this component, whereas a user with a single claim may receivea score of 8 and a user with five claims may receive a score of 0.

In at least some embodiments, at operation 304 the server 30 may use aplurality of inputs to determine the eligibility metric. For example,inputs received through multiple fields of the GUI may be evaluated togenerate a score. The score may, for example, be generate as a weightedaverage of scores associated with individual inputs, although othertechniques may also be used. The eligibility metric indicates a relativelikelihood of a user being eligible for a service.

At operation 306, the server 30 compares the eligibility metric topredefined eligibility criteria. The eligibility criteria may be storedin memory of the server 30 and may, for example, be a threshold, or arule. For example, the comparison at operation 306 may evaluate whetherthe eligibility metric is greater than or less than a threshold.

When the eligibility metric does not satisfy the eligibility criteria,control flow proceeds to operation 308 where the server 30 provides tothe remote computing device 20, via the communication system, a secondportion of the GUI. When the eligibility metric does satisfy theeligibility criteria, control flow proceeds to operation 310 where theserver 30 provides to the remote computing device 20, via thecommunication system, a third portion of the GUI.

The third portion of the GUI and the second portion of the GUI aredifferent. More specifically, the second portion of the GUI has agreater completion complexity than the third portion of the GUI. Thatis, the second portion of the GUI is the complex version of the GUI andthe third portion of the GUI is the non-complex version of the GUI.

As noted above, the second portion of the GUI (i.e., the complex versionof the GUI) may differ from the third portion of the GUI (i.e., thenon-complex version) in various aspects. For example, the second portionof the graphical user interface may include a false interface elementwhereas the third portion of the GUI does not include false interfaceelements. A false interface element may prompt for input that, oncereceived, is not stored or used by the server. That is, input that isreceived at the false interface element may simply be discarded and maynot be used, for example, in evaluating an application or formrepresented by the GUI. The false interface element only serves to makecompletion of the form or application more complicated.

By way of further example, the second portion of the graphical userinterface (i.e., the complex version) may be configured to disable anauto-completion function on the computing device whereas the thirdportion of the graphical user interface (i.e., the non-complex version)may not disable the auto-completion function. That is, the third portionof the GUI may be configured to enable the auto-completion function onthe computing device.

By way of further example, the second portion of the graphical userinterface may impose a formatting restriction that is not imposed by thethird portion of the graphical user interface. For example, the secondportion of the GUI may include an interface element for receiving afirst type of information and the third portion of the graphical userinterface may also include an interface element for receiving the firsttype of information. However, the interface element of the secondportion of the graphical user interface may impose a format restrictionthat is not enforced by the corresponding interface element of the thirdportion of the graphical user interface. For example, the formattingrestriction may be a date formatting restriction that requires aninputted date to accord to a predetermined format, a name formattingrestriction that requires an inputted name to accord to a predeterminedformat, a numerical formatting restriction, an address formattingrestriction such as a postal code formatting restriction, a contactinformation formatting restriction such as a telephone number formattingrestriction, or a formatting restriction of another type.

In some instances, the second portion of the GUI (i.e., the complexversion of the GUI) may differ from the third portion of the GUI (i.e.,the non-complex version) in that the second portion of the GUI does notprovide completion instructions that are provided on the third portionof the GUI. For example, the GUI may have completion requirements (e.g.,may require completion of certain fields or may enforce formattingrestrictions in certain fields) and the complex version of the documentmay not inform the user about such completion requirements when fieldsassociated with such completion requirements are displayed while thenon-complex version may inform the user about such completionrequirements while such fields are displayed. The complex version mayonly inform the user of the completion requirements after the userattempts to submit the form or application represented by the GUI,requiring the user to engage in a trial and error process in order tocomplete the form or application.

In some embodiments, the second portion of the graphical user interface(i.e., the complex version) and the third portion of the graphical userinterface (i.e., the non-complex version) may both include at least somecommon text but the font size of at least a portion of the common textmay be different on the second portion of the graphical user interfacethan on the third portion of the graphical user interface. Morespecifically, the second portion of the GUI may include a font that ispoorly sized. For example, the non-complex version of the GUI may use adefault font size for the browser, whereas the complex version mayoverride the default font size (e.g., by specifying an absolute size orby specifying a relative font size that is greater than or less than thedefault font size).

In some instances, the second portion of the GUI (i.e., the complexversion of the GUI) may differ from the third portion of the GUI (i.e.,the non-complex version) in that the second portion of the GUI includestext that is similar in content to text included in the third portion ofthe GUI but which has a higher word count than the text included in thethird portion of the GUI. That is, the second portion of the GUI may bea verbose version of the GUI.

In some instances, the second portion of the GUI (i.e., the complexversion of the GUI) and the third portion of the GUI (i.e., thenon-complex version) may include the same (non-dummy) interfaceelements. That is, both portions of the GUI may obtain the sameinformation but may simply do so in a different way.

Conveniently, since the server 30 is a computing device, it may evaluatethe inputs received from the remote computing device 20 in real time sothat the subsequent portion of the GUI can be provided instantly. Thatis, the determination may be made on-the-fly and unbeknownst to theuser. The GUI can be made to operate without lag due to the real-timeevaluation of the input by the server.

The techniques described herein may be used, for example, to dynamicallyrespond to congestion in a network or the server 30. For example, theserver 30 may monitor traffic and may modify the eligibility criteria todynamically control a computing resource associated with the server 30.For example, when traffic increases, the eligibility criteria may bemade more onerous so that a greater number of remote computing devicesreceive the relatively complex version of the GUI. Where the eligibilitycriteria is a threshold, this may be done by simply adjusting thethreshold. Later, when traffic slows, the eligibility criteria may bere-adjusted.

Reference is now made to FIG. 4, which is an example signal diagram 400diagrammatically illustrating signaling or messaging exchanged betweenthe server 30 and the remote computing device 20. The example signaldiagram 400 shows receipt, in operation 402, by the remote computingdevice 20 of an address associated with the server 30, such as a UniformResource Locator (URL). The address may, for example, be input into aURL bar associated with a web browser or may be received throughselection of a link associated with the address. Then, in operation 404,the remote computing device 20 requests a resource from the server 30.The request may be in the form of an HTTP GET.

In response to receiving the request, the server 30 retrieves a firstportion of the GUI (at operation 406) and sends the first portion of theGUI (at operation 408) to the remote computing device 20, which displaysthe first portion of the GUI at operation 410.

At operation 412, the remote computing device receives one or moreinputs through the GUI and sends a message containing the input(s) atoperation 414. The server 30 evaluates the input(s) at operation 416based on eligibility criteria and selects a next portion of the GUI toprovide. The next portion of the GUI is either the complex version ofthe GUI or the non-complex version of the GUI and the selection is madebased on the evaluation of the input(s). At operation 418, the server 30provides the next portion of the GUI to the remote computing device 20where it is displayed at operation 420.

It will be understood that the applications, modules, routines,processes, threads, or other software components implementing thedescribed method/process may be realized using standard computerprogramming techniques and languages. The present application is notlimited to particular processors, computer languages, computerprogramming conventions, data structures, or other such implementationdetails. Those skilled in the art will recognize that the describedprocesses may be implemented as a part of computer-executable codestored in volatile or non-volatile memory, as part of anapplication-specific integrated chip (ASIC), etc.

Certain adaptations and modifications of the described embodiments canbe made. Therefore, the above discussed embodiments are considered to beillustrative and not restrictive.

What is claimed is:
 1. A server to provide a graphical user interface toa computing device, the server comprising: a processor; a communicationsystem coupled to the processor for communicating over a network withthe computing device; and memory coupled to the processor and storingprocessor-readable instructions that, when executed, cause the processorto: provide, via the communication system and to the computing device, afirst portion of the graphical user interface, the first portion of thegraphical user interface including an interface element for receivinginput through an input interface associated with the computing device;receive, via the communication system, input received at the interfaceelement; determine an eligibility metric based on the input;automatically modify eligibility criteria by the server in response tochanges in network conditions; compare the eligibility metric to theeligibility criteria; and decrease a rate of submission of the inputwhen the eligibility metric does not satisfy the eligibility criteria,by providing, to the computing device via the communication system, asecond portion of the graphical user interface, the second portion ofthe graphical user interface having a greater completion complexity thana third portion of the graphical user interface, the third portion ofthe graphical user interface being provided when the eligibility metricsatisfies the eligibility criteria.
 2. The server of claim 1, whereinthe instructions, when executed, further cause the processor to: modifythe eligibility criteria to control a computing resource associated withthe server.
 3. The server of claim 1, wherein the second portion of thegraphical user interface includes a false interface element, the falseinterface element prompting for input that, once received, is not storedor used by the server.
 4. The server of claim 1, wherein the secondportion of the graphical user interface is configured to disable anauto-completion function on the computing device and wherein the thirdportion of the graphical user interface is configured to enable theauto-completion function on the computing device.
 5. The server of claim1, wherein the second portion of the graphical user interface includesan interface element for receiving a first type of information andwherein the third portion of the graphical user interface includes aninterface element for receiving the first type of information andwherein the interface element of the second portion of the graphicaluser interface imposes a format restriction that is not enforced by theinterface element of the third portion of the graphical user interface.6. The server of claim 5, wherein the format restriction includes a dateformatting restriction that requires an inputted date to accord to apredetermined format.
 7. The server of claim 5, wherein the formatrestriction is a name formatting restriction that requires an inputtedname to accord to a predetermined format.
 8. The server of claim 1,wherein the second portion of the graphical user interface and the thirdportion of the graphical user interface include at least some commontext and wherein a font size of at least a portion of the common text isdifferent on the second portion of the graphical user interface than onthe third portion of the graphical user interface.
 9. The server ofclaim 1, wherein the instructions, when executed, further cause theprocessor to: when the eligibility metric satisfies the eligibilitycriteria, providing, via the communication system, the third portion ofthe graphical user interface.
 10. The server of claim 1, wherein thesecond portion of the graphical user interface includes text similar incontent to text included in the third portion of the graphical userinterface but which has a higher word count than the text included inthe third portion of the graphical user interface.
 11. A method ofproviding a graphical user interface to a computing device, the methodcomprising: providing a first portion of the graphical user interface tothe computing device, the first portion of the graphical user interfaceincluding an interface element for receiving input through an inputinterface associated with the computing device; receiving input receivedat the interface element; determining an eligibility metric based on theinput; automatically modify eligibility criteria by a server in responseto changes in network conditions; comparing the eligibility metric tothe eligibility criteria; and decreasing a rate of submission of theinput when the eligibility metric does not satisfy the eligibilitycriteria, by providing, to the computing device, a second portion of thegraphical user interface, the second portion of the graphical userinterface having a greater completion complexity than a third portion ofthe graphical user interface, the third portion of the graphical userinterface being provided when the eligibility metric satisfies theeligibility criteria.
 12. The method of claim 11, further comprising:modifying the eligibility criteria to control a computing resourceassociated with the server.
 13. The method of claim 11, wherein thesecond portion of the graphical user interface includes a falseinterface element, the false interface element prompting for input that,once received, is not stored or used.
 14. The method of claim 11,wherein the second portion of the graphical user interface is configuredto disable an auto-completion function on the computing device andwherein the third portion of the graphical user interface is configuredto enable the auto-completion function on the computing device.
 15. Themethod of claim 11, wherein the second portion of the graphical userinterface includes an interface element for receiving a first type ofinformation and wherein the third portion of the graphical userinterface includes an interface element for receiving the first type ofinformation and wherein the interface element of the second portion ofthe graphical user interface imposes a format restriction that is notenforced by the interface element of the third portion of the graphicaluser interface.
 16. The method of claim 15, wherein the formatrestriction includes a date formatting restriction that requires aninputted date to accord to a predetermined format.
 17. The method ofclaim 15, wherein the format restriction includes a name formattingrestriction that requires an inputted name to accord to a predeterminedformat.
 18. The method of claim 11, wherein the second portion of thegraphical user interface and the third portion of the graphical userinterface include at least some common text and wherein a font size ofat least a portion of the common text is different on the second portionof the graphical user interface than on the third portion of thegraphical user interface.
 19. The method of claim 11, furthercomprising: when the eligibility metric satisfies the eligibilitycriteria, providing the third portion of the graphical user interface.20. A non-transitory computer readable storage medium comprisingprocessor-executable instructions which, when executed, configure aprocessor to: provide a first portion of a graphical user interface to acomputing device, the first portion of the graphical user interfaceincluding an interface element for receiving input through an inputinterface associated with the computing device; receive input receivedat the interface element; determine an eligibility metric based on theinput; automatically modify eligibility criteria by a server in responseto changes in network conditions; compare the eligibility metric to theeligibility criteria; and decrease a rate of submission of the inputwhen the eligibility metric does not satisfy the eligibility criteria,by providing, to the computing device, a second portion of the graphicaluser interface, the second portion of the graphical user interfacehaving a greater completion complexity than a third portion of thegraphical user interface, the third portion of the graphical userinterface being provided when the eligibility metric satisfies theeligibility criteria.